OCPBUGS-79667: Use feature-gate annotation for Sail Library RBAC by gcs278 · Pull Request #1393 · openshift/cluster-ingress-operator

gcs278 · 2026-03-19T18:57:21Z

Summary

Replace feature-set annotations with the new release.openshift.io/feature-gate annotation to conditionally deploy Sail Library RBAC based on the GatewayAPI feature gate state.

This leverages the new CVO capability that applies manifests based on enabled feature gates, allowing atomic feature promotion without manual payload adjustments.

Problem

The CVO only includes TechPreview-annotated manifests in the release payload during cluster installation. When the feature set is changed on a running cluster:

The CVO restarts with the new feature set
But the payload manifests remain filtered based on the original install-time feature set
TechPreview manifests are permanently unavailable on clusters installed with the Default feature set

This means if a cluster is installed with Default feature set, the Sail Library RBAC manifests would never be applied, even if a user enables TechPreviewNoUpgrade later and creates a GatewayClass.

Solution

Use the new release.openshift.io/feature-gate: GatewayAPI annotation instead of release.openshift.io/feature-set: TechPreviewNoUpgrade on:

manifests/00-cluster-role-sail-library.yaml
manifests/01-cluster-role-binding-sail-library.yaml

The CVO will apply these manifests when the GatewayAPI feature gate is enabled, eliminating the install-time filtering limitation. This approach allows:

Manifests to be applied dynamically based on feature gate state
Atomic feature promotion without adjusting conditional manifests
Gateway API functionality on any cluster with the feature gate enabled

Context

Depends on OCPSTRAT-2485: Introduce feature gate based inclusion/exclusion of manifests cluster-version-operator#1273 (feature-gate annotation support)
The new annotation replaces release.openshift.io/feature-set in most cases
Format: release.openshift.io/feature-gate: Foo,-Bar applies when Foo is enabled and Bar is disabled
Required before NE-2520: Promote GatewayAPIWithoutOLM to GA api#2772 (promoting GatewayAPIWithoutOLM to Default feature set)

🤖 Generated with Claude Code

openshift-ci-robot · 2026-03-19T18:57:25Z

@gcs278: This pull request references NE-2471 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Remove TechPreviewNoUpgrade annotation from Sail ClusterRole and ClusterRoleBinding to avoid breakage when GatewayAPIWithoutOLM is promoted to GA.

Required to merge before openshift/api#2772

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

coderabbitai · 2026-03-19T18:57:40Z

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: da54b1ed-69bc-4000-b0cd-f756c6a184c2

📥 Commits

Reviewing files that changed from the base of the PR and between ed0eb2b and b088953.

📒 Files selected for processing (2)

manifests/00-cluster-role-sail-library.yaml
manifests/01-cluster-role-binding-sail-library.yaml

✅ Files skipped from review due to trivial changes (1)

manifests/00-cluster-role-sail-library.yaml

🚧 Files skipped from review as they are similar to previous changes (1)

manifests/01-cluster-role-binding-sail-library.yaml

📝 Walkthrough

Walkthrough

Updated annotations in two manifests: manifests/00-cluster-role-sail-library.yaml (ClusterRole metadata.annotations) and manifests/01-cluster-role-binding-sail-library.yaml (ClusterRoleBinding metadata.annotations). In each file the release.openshift.io/feature-set: DevPreviewNoUpgrade,TechPreviewNoUpgrade entry was removed and release.openshift.io/feature-gate: GatewayAPIWithoutOLM was added. No other fields, RBAC rules, subjects, roleRef, apiVersion, or kind were changed.

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

openshift-ci · 2026-03-19T19:01:37Z

@gcs278: This PR was included in a payload test run from openshift/origin#30897
trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-gcp-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/0ab81910-23c6-11f1-8635-bf728c1f5aad-0

openshift-ci · 2026-03-20T02:40:25Z

@gcs278: This PR was included in a payload test run from openshift/origin#30897
trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-gcp-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/1e4a3720-2406-11f1-93e5-9f16732fd0e5-0

openshift-ci · 2026-03-20T19:29:09Z

@gcs278: This PR was included in a payload test run from openshift/origin#30897
trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-gcp-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/0ddd5ec0-2493-11f1-8cf8-effe9a495bea-0

openshift-ci · 2026-03-21T01:51:06Z

@gcs278: This PR was included in a payload test run from openshift/origin#30897
trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-gcp-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/69a77f80-24c8-11f1-9403-ad1a7c99fb97-0

openshift-ci · 2026-03-21T01:52:00Z

@gcs278: This PR was included in a payload test run from openshift/origin#30897
trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-gcp-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/8a761690-24c8-11f1-9c74-da2cb51d6692-0

gcs278 · 2026-03-23T18:05:04Z

/test e2e-gcp-ovn-techpreview

openshift-ci · 2026-03-23T23:31:37Z

@gcs278: This PR was included in a payload test run from openshift/origin#30897
trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-gcp-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/6d5568f0-2710-11f1-9d03-561b26d4f2f7-0

openshift-ci-robot · 2026-03-25T20:00:25Z

@gcs278: This pull request references NE-2471 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Summary

Remove TechPreviewNoUpgrade annotations from Sail Library ClusterRole and ClusterRoleBinding to enable Gateway API functionality on all OpenShift clusters as we promote to GA.

Problem

The CVO only includes TechPreview-annotated manifests in the release payload during cluster installation. When the feature set is changed on a running cluster:

The CVO restarts with the new feature set

But the payload manifests remain filtered based on the original install-time feature set

TechPreview manifests are permanently unavailable on clusters installed with the Default feature set

This means if a cluster is installed with Default feature set, the Sail Library RBAC manifests would never be applied, even if a user enables TechPreviewNoUpgrade later and creates a GatewayClass.

Solution

Remove the release.openshift.io/feature-set: TechPreviewNoUpgrade annotations from:

manifests/00-cluster-role-sail-library.yaml

manifests/01-cluster-role-binding-sail-library.yaml

This ensures the Sail Library RBAC is included in all cluster installations, allowing Gateway API to function correctly as we promote the feature to GA.

Context

Required before NE-2520: Promote GatewayAPIWithoutOLM to GA api#2772 (promoting GatewayAPIWithoutOLM to Default feature set)

See CVO code: https://github.com/openshift/cluster-version-operator/blob/master/pkg/cvo/cvo.go#L179-L186

🤖 Generated with Claude Code

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

openshift-ci-robot · 2026-03-25T20:36:49Z

@gcs278: This pull request references Jira Issue OCPBUGS-79667, which is invalid:

expected the bug to target the "4.22.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Summary

Remove TechPreviewNoUpgrade annotations from Sail Library ClusterRole and ClusterRoleBinding to enable Gateway API functionality on all OpenShift clusters as we promote to GA.

Problem

The CVO only includes TechPreview-annotated manifests in the release payload during cluster installation. When the feature set is changed on a running cluster:

The CVO restarts with the new feature set

But the payload manifests remain filtered based on the original install-time feature set

TechPreview manifests are permanently unavailable on clusters installed with the Default feature set

This means if a cluster is installed with Default feature set, the Sail Library RBAC manifests would never be applied, even if a user enables TechPreviewNoUpgrade later and creates a GatewayClass.

Solution

Remove the release.openshift.io/feature-set: TechPreviewNoUpgrade annotations from:

manifests/00-cluster-role-sail-library.yaml

manifests/01-cluster-role-binding-sail-library.yaml

This ensures the Sail Library RBAC is included in all cluster installations, allowing Gateway API to function correctly as we promote the feature to GA.

Context

Required before NE-2520: Promote GatewayAPIWithoutOLM to GA api#2772 (promoting GatewayAPIWithoutOLM to Default feature set)

See CVO code: https://github.com/openshift/cluster-version-operator/blob/master/pkg/cvo/cvo.go#L179-L186

🤖 Generated with Claude Code

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

gcs278 · 2026-03-25T20:37:02Z

/jira refresh

openshift-ci-robot · 2026-03-25T20:37:12Z

@gcs278: This pull request references Jira Issue OCPBUGS-79667, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.22.0) matches configured target version for branch (4.22.0)
bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (iamin@redhat.com), skipping review request.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

gcs278 · 2026-03-26T20:26:48Z

/unhold

Updated to release.openshift.io/feature-gate

rhamini3 · 2026-03-26T20:40:57Z

/verified by @rhamini3

openshift-ci-robot · 2026-03-26T20:41:10Z

@rhamini3: This PR has been marked as verified by @rhamini3.

Details

In response to this:

/verified by @rhamini3

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

openshift-ci-robot · 2026-03-26T23:04:12Z

/retest-required

Remaining retests: 0 against base HEAD a6176ea and 2 for PR HEAD b088953 in total

openshift-ci · 2026-03-27T00:47:40Z

@gcs278: This PR was included in a payload test run from openshift/origin#30897
trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-gcp-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/8ca6afd0-2976-11f1-87dd-3a0e2dc903f1-0

openshift-ci · 2026-03-27T01:01:54Z

@gcs278: This PR was included in a payload test run from openshift/origin#30897
trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-gcp-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/899a4840-2978-11f1-88a5-2fdf52f0125a-0

openshift-ci · 2026-03-27T01:08:42Z

@gcs278: This PR was included in a payload test run from openshift/origin#30897
trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-gcp-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/7c1b46a0-2979-11f1-9476-ac2dbf9a0ed8-0

openshift-ci · 2026-03-27T01:12:41Z

@gcs278: This PR was included in a payload test run from openshift/origin#30897
trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-gcp-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/0ad0efd0-297a-11f1-95c5-290d9ec10095-0

openshift-ci-robot · 2026-03-27T02:04:19Z

/retest-required

Remaining retests: 0 against base HEAD d16dd45 and 1 for PR HEAD b088953 in total

lihongan · 2026-03-27T08:22:32Z

/retest-required

gcs278 · 2026-03-27T13:33:48Z

Teardown failure in hypershift
/test e2e-hypershift

openshift-ci · 2026-03-27T13:39:37Z

@gcs278: This PR was included in a payload test run from openshift/origin#30897
trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-gcp-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/61957ad0-29e2-11f1-9921-6bbab26a3719-0

Miciah · 2026-03-27T16:39:05Z

The commit message says "based on the GatewayAPI feature gate state" but should say "based on the GatewayAPIWithoutOLM feature gate". However, it isn't worth doing another force-push just to fix that issue.

openshift-ci-robot · 2026-03-27T19:04:21Z

/retest-required

Remaining retests: 0 against base HEAD dde7a93 and 0 for PR HEAD b088953 in total

openshift-ci-robot · 2026-03-27T21:04:19Z

/hold

Revision b088953 was retested 3 times: holding

gcs278 · 2026-03-27T21:30:23Z

e2e-hypershift is about 50% succeeding, and mostly flaking on teardowns, though I did see one TestNodePool/HostedCluster0/Main/TestNodePoolInPlaceUpgrade failure that wasn't Teardown.

/test e2e-hypershift

openshift-ci-robot · 2026-03-27T22:04:15Z

/retest-required

Remaining retests: 0 against base HEAD dde7a93 and 2 for PR HEAD b088953 in total

gcs278 · 2026-03-27T23:14:24Z

/test e2e-hypershift

rikatz · 2026-03-28T06:55:26Z

/retest-required

rikatz · 2026-03-29T05:47:12Z

/retest-required

gcs278 · 2026-03-29T22:45:21Z

e2e-aws-operator pod failed to schedule, and the failures in e2e-aws-ovn-serial-2-of2 look unrelated:
/retest

openshift-ci · 2026-03-29T22:47:05Z

@gcs278: This PR was included in a payload test run from openshift/origin#30897
trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-gcp-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/322df070-2bc1-11f1-9068-51d08a5996e8-0

openshift-ci · 2026-03-30T01:53:13Z

@gcs278: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

openshift-ci-robot · 2026-03-30T01:57:05Z

@gcs278: Jira Issue Verification Checks: Jira Issue OCPBUGS-79667
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-79667 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

Summary

Replace feature-set annotations with the new release.openshift.io/feature-gate annotation to conditionally deploy Sail Library RBAC based on the GatewayAPI feature gate state.

This leverages the new CVO capability that applies manifests based on enabled feature gates, allowing atomic feature promotion without manual payload adjustments.

Problem

The CVO only includes TechPreview-annotated manifests in the release payload during cluster installation. When the feature set is changed on a running cluster:

The CVO restarts with the new feature set

But the payload manifests remain filtered based on the original install-time feature set

TechPreview manifests are permanently unavailable on clusters installed with the Default feature set

This means if a cluster is installed with Default feature set, the Sail Library RBAC manifests would never be applied, even if a user enables TechPreviewNoUpgrade later and creates a GatewayClass.

Solution

Use the new release.openshift.io/feature-gate: GatewayAPI annotation instead of release.openshift.io/feature-set: TechPreviewNoUpgrade on:

manifests/00-cluster-role-sail-library.yaml

manifests/01-cluster-role-binding-sail-library.yaml

The CVO will apply these manifests when the GatewayAPI feature gate is enabled, eliminating the install-time filtering limitation. This approach allows:

Manifests to be applied dynamically based on feature gate state

Atomic feature promotion without adjusting conditional manifests

Gateway API functionality on any cluster with the feature gate enabled

Context

Depends on OCPSTRAT-2485: Introduce feature gate based inclusion/exclusion of manifests cluster-version-operator#1273 (feature-gate annotation support)

The new annotation replaces release.openshift.io/feature-set in most cases

Format: release.openshift.io/feature-gate: Foo,-Bar applies when Foo is enabled and Bar is disabled

Required before NE-2520: Promote GatewayAPIWithoutOLM to GA api#2772 (promoting GatewayAPIWithoutOLM to Default feature set)

🤖 Generated with Claude Code

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

openshift-merge-robot · 2026-04-01T17:33:54Z

Fix included in accepted release 4.22.0-0.nightly-2026-04-01-092906

openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 19, 2026

gcs278 marked this pull request as draft March 19, 2026 18:57

openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 19, 2026

openshift-ci bot requested review from jcmoraisjr and miheer March 19, 2026 18:58

gcs278 mentioned this pull request Mar 19, 2026

NE-2561: Add Gateway API OLM to NO-OLM migration upgrade test openshift/origin#30897

Merged

gcs278 force-pushed the sail-clusterrole-GA branch from 790388c to a51eaff Compare March 25, 2026 19:59

gcs278 marked this pull request as ready for review March 25, 2026 20:01

openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 25, 2026

openshift-ci bot requested review from bentito and davidesalerno March 25, 2026 20:02

gcs278 force-pushed the sail-clusterrole-GA branch from a51eaff to ed0eb2b Compare March 25, 2026 20:36

gcs278 changed the title ~~NE-2471: Remove feature-set annotations from Sail Library RBAC~~ OCPBUGS-79667: Remove feature-set annotations from Sail Library RBAC Mar 25, 2026

openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Mar 25, 2026

openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Mar 25, 2026

openshift-ci bot assigned alebedev87 Mar 26, 2026

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 26, 2026

openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 26, 2026

openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Mar 26, 2026

openshift-merge-bot bot merged commit 019903c into openshift:master Mar 30, 2026
19 checks passed

Conversation

gcs278 commented Mar 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Problem

Solution

Context

Uh oh!

openshift-ci-robot commented Mar 19, 2026 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

coderabbitai bot commented Mar 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Uh oh!

openshift-ci bot commented Mar 19, 2026

Uh oh!

openshift-ci bot commented Mar 20, 2026

Uh oh!

openshift-ci bot commented Mar 20, 2026

Uh oh!

openshift-ci bot commented Mar 21, 2026

Uh oh!

openshift-ci bot commented Mar 21, 2026

Uh oh!

gcs278 commented Mar 23, 2026

Uh oh!

openshift-ci bot commented Mar 23, 2026

Uh oh!

openshift-ci-robot commented Mar 25, 2026 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Problem

Solution

Context

Uh oh!

openshift-ci-robot commented Mar 25, 2026

Summary

Problem

Solution

Context

Uh oh!

gcs278 commented Mar 25, 2026

Uh oh!

openshift-ci-robot commented Mar 25, 2026

Uh oh!

gcs278 commented Mar 26, 2026

Uh oh!

rhamini3 commented Mar 26, 2026

Uh oh!

openshift-ci-robot commented Mar 26, 2026

Uh oh!

openshift-ci-robot commented Mar 26, 2026

Uh oh!

openshift-ci bot commented Mar 27, 2026

Uh oh!

openshift-ci bot commented Mar 27, 2026

Uh oh!

openshift-ci bot commented Mar 27, 2026

Uh oh!

openshift-ci bot commented Mar 27, 2026

Uh oh!

openshift-ci-robot commented Mar 27, 2026

Uh oh!

lihongan commented Mar 27, 2026

Uh oh!

gcs278 commented Mar 27, 2026

Uh oh!

openshift-ci bot commented Mar 27, 2026

Uh oh!

Miciah commented Mar 27, 2026

Uh oh!

openshift-ci-robot commented Mar 27, 2026

Uh oh!

openshift-ci-robot commented Mar 27, 2026

Uh oh!

gcs278 commented Mar 27, 2026

Uh oh!

openshift-ci-robot commented Mar 27, 2026

Uh oh!

gcs278 commented Mar 19, 2026 •

edited

Loading

openshift-ci-robot commented Mar 19, 2026 •

edited by openshift-ci bot

Loading

coderabbitai bot commented Mar 19, 2026 •

edited

Loading

openshift-ci-robot commented Mar 25, 2026 •

edited by openshift-ci bot

Loading